Skip to content

fix(ENG-57298): use absolute URLs for llms.txt links - #613

Merged
ketanyekale merged 1 commit into
mainfrom
docs/ENG-57298-fix-llms-txt-links
Nov 17, 2026
Merged

ketanyekale merged 1 commit into
mainfrom
docs/ENG-57298-fix-llms-txt-links

Conversation

@raj-dubey1

Copy link
Copy Markdown
Contributor

Description

The Mintlify link-rot check fails on every docs PR (e.g. #609) with 3 broken links that live on main, not in the PR:

  • design-system.mdx: [llms.txt](/llms.txt)
  • llms-index.mdx: [/docs/llms.txt](/llms.txt) and [/docs/llms-full.txt](/llms-full.txt)

Mintlify generates /llms.txt and /llms-full.txt at serve time. They aren't files in the repo, so the link checker treats them as missing. This PR points the 3 links at the live absolute URLs (https://www.cometchat.com/docs/llms.txt and https://www.cometchat.com/docs/llms-full.txt). The link text and the pages they reach don't change.

Verification

Related Issue(s)

Multica: ENG-57298 (https://multica.cometchat-staging.com/rnd-team/issues/ENG-57298)

Type of Change

  • Documentation correction/update
  • New documentation
  • Improvement to existing documentation
  • Typo fix
  • Other (please specify)

Checklist

  • I have read the CONTRIBUTING document
  • My branch name follows the naming convention
  • My changes follow the documentation style guide
  • I have checked for spelling and grammar errors
  • All links in my changes are valid and working
  • My changes are accurately described in this pull request

Additional Information

Two lines changed in two files. Once this merges, open docs PRs need a rebase or re-run to pick up a green link-rot check.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WEaVigCRBjkftm78T25MQA

/llms.txt and /llms-full.txt are generated by Mintlify at serve time, so
they are not files in the repo and the link-rot check flags them on every
PR. Point the 3 links in design-system.mdx and llms-index.mdx at the live
https://www.cometchat.com/docs/ URLs instead.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WEaVigCRBjkftm78T25MQA
@mintlify

mintlify Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
cometchat 🟢 Ready View Preview Nov 16, 2026, 2:34 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

@ketanyekale ketanyekale left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving on Ketan's instruction after review at 8a08fe5.

Verdict: APPROVE — no blocking findings.

The diagnosis is correct: /llms.txt and /llms-full.txt are generated by Mintlify at serve time, so they are not repo files and the link checker counts them as missing. The verification method is sound — mint broken-links on unmodified main returned the same 3, confirming they are pre-existing on main rather than introduced by any PR. link-rot now passes on this branch.

Absolute https://www.cometchat.com/docs/ links are already the existing convention in at least 20 other files (ai-agents.mdx, cli.mdx, agent-skills.mdx, several UI Kit overviews), so this sets no new precedent.

Non-blocking, worth a follow-up: in llms-index.mdx the original was [/docs/llms.txt](/llms.txt) — link text saying /docs/, href saying /. If Mintlify does not prefix the docs base path onto root-relative hrefs, those links were broken for readers too, not only for the checker. Worth checking whether other root-relative links in the repo carry the same mismatch; the three fixed here may be a sample rather than the set.

@ketanyekale
ketanyekale merged commit 85c7900 into main Nov 17, 2026
5 checks passed

This branch was successfully deployed

1 active deployment
staging — 8a08fe5d Deployed Nov 16, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants